Method and apparatus for counting devices related to broadcast data services

ABSTRACT

Methods and apparatuses are provided that include counting devices for broadcast data services. The devices can be counted based on registrations received from the devices. This registration count can additionally or alternatively be used to determine whether further counting is desired. In addition, base stations can transmit counting requests to the devices using a paging message or other message such that idle mode devices can receive the counting requests. The idle mode devices can respond to the requests or send autonomous counting report by switching to an active mode for the purpose of responding or another purpose.

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

The present application for patent claims priority to ProvisionalApplication No. 61/440,800, entitled “SYSTEMS AND METHODS FOR PROVIDINGSERVICES IN A WIRELESS NETWORK” filed Feb. 8, 2011, and ProvisionalApplication No. 61/506,512, entitled “SYSTEMS AND METHODS FOR PROVIDINGBROADCAST/MULTICAST SERVICES IN A WIRELESS NETWORK” filed Jul. 11, 2011,which are assigned to the assignee hereof and hereby expresslyincorporated by reference herein.

BACKGROUND

1. Field

The following description relates generally to wireless networkcommunications, and more particularly to broadcast/multicast services.

2. Background

Wireless communication systems are widely deployed to provide varioustypes of communication content such as, for example, voice, data, and soon. Typical wireless communication systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing available system resources (e.g., bandwidth, transmit power, . .. ). Examples of such multiple-access systems may include code divisionmultiple access (CDMA) systems, time division multiple access (TDMA)systems, frequency division multiple access (FDMA) systems, orthogonalfrequency division multiple access (OFDMA) systems, and the like.Additionally, the systems can conform to specifications such as thirdgeneration partnership project (3GPP) (e.g., 3GPP LTE (Long TermEvolution)/LTE-Advanced), ultra mobile broadband (UMB), evolution dataoptimized (EV-DO), etc.

Generally, wireless multiple-access communication systems maysimultaneously support communication for multiple mobile devices. Eachmobile device may communicate with one or more base stations viatransmissions on forward and reverse links. The forward link (ordownlink) refers to the communication link from base stations to mobiledevices, and the reverse link (or uplink) refers to the communicationlink from mobile devices to base stations. Further, communicationsbetween mobile devices and base stations may be established viasingle-input single-output (SISO) systems, multiple-input single-output(MISO) systems, multiple-input multiple-output (MIMO) systems, and soforth.

Base stations can also provide broadcast/multicast communications to oneor more devices. In one example, the base stations can broadcast signalsincluding data for multiple services within one or more subframes orother periods of time. In this example, the devices can obtain certaindata from the signals; for example, the devices can subscribe to aservice from the one or more base stations that broadcasts the signals,and in one example, can receive corresponding instructions for decodingthe data from the signals. Examples of broadcast services can includeMultimedia Broadcast and Multicast Service (MBMS), evolved MBMS (eMBMS),both of which are defined in LTE, and/or similar broadcast services forother network types.

Furthermore, eMBMS for example, provides a network-based countingprocedure to obtain a number of devices receiving or decoding thebroadcast signals from a base station by requesting the base station tobroadcast a Counting Request. The Counting Request can identify certaindevices, for example, and the devices receiving the Counting Request anddetermining that the request relates to the device can respond with aCounting Response over a unicast channel. Based on the responsesreceived, the base station can determine a count of devices receivingbroadcast services from the base station, and can report the count tothe network. The count, however, may not be accurate as it only measuresdevices in a connected mode. In addition, such a polling procedure mayrequire devices to wake up during certain time intervals and expendradio resources to respond to the Counting Request.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In accordance with one or more aspects and corresponding disclosurethereof, the present disclosure describes various aspects in connectionwith improving counting procedures for broadcast data services. Forexample, various counting procedures are described that consider idlemode devices, utilize radio resources more efficiently, and/or the like.In one example, a registration-based counting can be provided where anetwork counts devices upon receiving a registration for a broadcastservice. In another example, the network can determine whether to enablecounting and/or whether to send a counting request for refined countingbased on the number of devices currently registered to receive theservice. Moreover, for example, idle mode devices can report counting aspart of a random access procedure, in response to a counting request,and/or the like. This can include deferring reporting until the deviceswitches to an active mode (e.g., for a purpose other than responding tothe counting request). In other examples, the counting can be based onother device-based behavior, such as activating/deactivating broadcastservice, autonomous reporting by the devices, etc.

According to an example, a method for counting devices related tobroadcast data is provided. The method includes receiving a registrationrequest for broadcast data related to a device and incrementing aregistration count based in part on the receiving the registrationrequest. The method further includes determining whether to enablecounting of devices from one or more base stations based in part on theregistration count.

In another aspect, an apparatus for counting devices related tobroadcast data is provided. The apparatus means for receiving aregistration request for broadcast data related to a device and meansfor incrementing a registration count based in part on the registrationrequest. The apparatus further includes means for determining whether torequest counting of devices from one or more base stations based in parton the registration count.

In yet another aspect, an apparatus for wireless communication isprovided that includes at least one processor configured to receive aregistration request for broadcast data related to a device, increment aregistration count based in part on the registration request, anddetermine whether to request counting of devices from one or more basestations based in part on the registration count. The apparatus furtherincludes a memory coupled to the at least one processor.

Still, in another aspect, a computer-program product for countingdevices related to broadcast data is provided including a non-transitorycomputer-readable medium having code for causing at least one computerto receive a registration request for broadcast data related to adevice. The computer-readable medium further includes code for causingthe at least one computer to increment a registration count based inpart on the registration request and code for causing the at least onecomputer to determine whether to request counting of devices from one ormore base stations based in part on the registration count.

Moreover, in an aspect, an apparatus for counting devices related tobroadcast data is provided that includes a registration informationreceiving component for receiving a registration request for broadcastdata related to a device and a device counting component forincrementing a registration count based in part on the registrationrequest. The apparatus further includes a counting request determiningcomponent for determining whether to request counting of devices fromone or more base stations based in part on the registration count.

According to another example, a method for responding to a countingrequest for multicast broadcast data is provided. The method includesreceiving a counting request from a base station while communicating inan idle mode with the base station and switching to an active mode forcommunicating with the base station. The method further includesresponding to the counting request while in the active mode.

In another aspect, an apparatus for broadcast communication with a basestation is provided. The apparatus includes means for receiving acounting request related to receiving broadcast data from a base stationwhile communicating in an idle mode with the base station and means forswitching to an active mode for communicating with the base station. Theapparatus further includes means for responding to the counting requestwhile in the active mode.

In yet another aspect, an apparatus for wireless communication isprovided that includes at least one processor configured to receive acounting request related to receiving broadcast data from a base stationwhile communicating in an idle mode with the base station, switch to anactive mode for communicating with the base station, and respond to thecounting request while in the active mode. The apparatus furtherincludes a memory coupled to the at least one processor.

Still, in another aspect, a computer-program product for broadcastcommunication with a base station is provided including a non-transitorycomputer-readable medium having code for causing at least one computerto receive a counting request related to receiving broadcast data from abase station while communicating in an idle mode with the base station.The computer-readable medium further includes code for causing the atleast one computer to switch to an active mode for communicating withthe base station and code for causing the at least one computer torespond to the counting request while in the active mode.

Moreover, in an aspect, an apparatus for broadcast communication with abase station is provided that includes a counting request receivingcomponent for receiving a counting request related to receivingbroadcast data from a base station while communicating in an idle modewith the base station and a communication mode component for switchingto an active mode for communicating with the base station. The apparatusfurther includes a counting request responding component for respondingto the counting request while in the active mode.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements, andin which:

FIG. 1 is a multiple access wireless communication system according toan embodiment described herein.

FIG. 2 is a block diagram of a communication system according to anembodiment described herein.

FIG. 3 is a block diagram of a wireless communication network forproviding broadcast data communication.

FIG. 4 is a block diagram of various components that may be utilized ina wireless communication system.

FIG. 5 is an example communication configuration from a base stationcommunicating broadcast data.

FIG. 6 is an aspect of an example system for counting deviceregistrations.

FIG. 7 is an aspect of an example system for counting devicesregistering to receive broadcast data.

FIG. 8 is an aspect of an example system for counting devicesregistering to receive broadcast data over hyper text transfer protocol.

FIG. 9 is an aspect of an example system for requesting a counting ofdevices receiving or interested in receiving broadcast data.

FIG. 10 is an aspect of an example system for responding to countingrequests received in idle mode communications.

FIG. 11 is an aspect of an example system for counting devices receivingor interested in receiving broadcast data including idle mode devices.

FIG. 12 is an aspect of an example system for counting devices receivingor interested in receiving broadcast data based onactivation/deactivation of the broadcast service.

FIG. 13 is an aspect of an example system for counting devices receivingor interested in receiving broadcast data by responding to countingrequests after a period of time.

FIG. 14 is a flow chart of an aspect of a methodology for obtainingbroadcast data.

FIG. 15 is a flow chart of an aspect of a methodology for determiningwhether to enable counting based on a registration count.

FIG. 16 is a flow chart of an aspect of a methodology for determiningwhether to activate multicast broadcast services based on a registrationcount.

FIG. 17 is a flow chart of an aspect of a methodology for responding tocounting requests.

FIG. 18 is a block diagram of an example system that determines whetherto enable counting based on a registration count.

FIG. 19 is a block diagram of an example system that responds tocounting requests.

FIG. 20 is a block diagram of an aspect of an example mobile device inaccordance with aspects described herein.

FIG. 21 is a block diagram of an aspect of a computer device inaccordance with aspects described herein.

FIG. 22 is a block diagram of an example system in accordance withaspects described herein.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

Described further herein are various considerations related to improvingcounting of devices that receive and/or would like to receive data fromone or more broadcast services. For example, counting can be based ondevice registration for the broadcast service. Thus, for example, uponreceiving a registration request from a device, a network can incrementa count of devices (e.g., and/or can decrement the count upon receivinga deregistration request). In addition, the network can determinewhether to obtain a more accurate count by transmitting countingrequests based in part on the number of registered devices reported bythe base station. In another example, devices communicating in an idlemode can be counted by allowing the devices to switch to an active modeand transmit a counting response. In an example, the device can switchto the active mode for another purpose, but can respond to a previouscounting request while in active mode. Moreover, in other examples,devices can autonomously report counting to the base station, reportcounting when activating/deactivating receiving the broadcast data,and/or the like.

As used in this application, the terms “component,” “module,” “system”and the like are intended to include a computer-related entity, such asbut not limited to hardware, firmware, a combination of hardware andsoftware, software, or software in execution, etc. For example, acomponent may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a computing device and the computing device canbe a component. One or more components can reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. In addition,these components can execute from various computer readable media havingvarious data structures stored thereon. The components may communicateby way of local and/or remote processes such as in accordance with asignal having one or more data packets, such as data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsby way of the signal.

Furthermore, various aspects are described herein in connection with aterminal, which can be a wired terminal or a wireless terminal. Aterminal can also be called a system, device, subscriber unit,subscriber station, mobile station, mobile, mobile device, remotestation, remote terminal, access terminal, user terminal, terminal,communication device, user agent, user device, or user equipment (UE),etc. A wireless terminal may be a cellular telephone, a satellite phone,a cordless telephone, a Session Initiation Protocol (SIP) phone, awireless local loop (WLL) station, a personal digital assistant (PDA), ahandheld device having wireless connection capability, a computingdevice, a tablet, a smart book, a netbook, or other processing devicesconnected to a wireless modem, etc. Moreover, various aspects aredescribed herein in connection with a base station. A base station maybe utilized for communicating with wireless terminal(s) and may also bereferred to as an access point, a Node B, evolved Node B (eNB), or someother terminology.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS,LTE/LTE-Advanced and GSM are described in documents from an organizationnamed “3rd Generation Partnership Project” (3GPP). Additionally,cdma2000 and UMB are described in documents from an organization named“3rd Generation Partnership Project 2” (3GPP2). Further, such wirelesscommunication systems may additionally include peer-to-peer (e.g.,mobile-to-mobile) ad hoc network systems often using unpaired unlicensedspectrums, 802.xx wireless LAN, BLUETOOTH and any other short- orlong-range, wireless communication techniques.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches may also be used.

Referring to FIG. 1, a multiple access wireless communication systemaccording to one embodiment is illustrated. An access point 100 (AP)includes multiple antenna groups, one including 104 and 106, anotherincluding 108 and 110, and an additional including 112 and 114. In FIG.1, only two antennas are shown for each antenna group, however, more orfewer antennas may be utilized for each antenna group. Access terminal116 (AT) is in communication with antennas 112 and 114, where antennas112 and 114 transmit information to access terminal 116 over forwardlink 120 and receive information from access terminal 116 over reverselink 118. Access terminal 122 is in communication with antennas 104 and106, where antennas 104 and 106 transmit information to access terminal122 over forward link 126 and receive information from access terminal122 over reverse link 124. In a frequency division duplex (FDD) system,communication links 118, 120, 124 and 126 may use different frequencyfor communication. For example, forward link 120 may use a differentfrequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access point. Insome aspects, antenna groups each are designed to communicate to accessterminals in a sector of the areas covered by access point 100.

In communication over forward links 120 and 126, the transmittingantennas of access point 100 may utilize beamforming in order to improvethe signal-to-noise ratio of forward links for the different accessterminals 116 and 122. Also, an access point using beamforming totransmit to access terminals scattered randomly through its coveragecauses less interference to access terminals in neighboring cells thanan access point transmitting through a single antenna to all its accessterminals.

An access point may be a fixed station used for communicating with theterminals and may also be referred to as an access point, a Node B,evolved Node B (eNB), or some other terminology. An access terminal mayalso be called an access terminal, UE, device, a wireless communicationdevice, terminal, access terminal or some other terminology. Moreover,an access point can be a macrocell access point, femtocell access point,picocell access point, and/or the like.

In various embodiments, as described herein, one or more segments or oneor more extension carriers can be linked to a regular carrier resultingin a composite bandwidth over which the UE can transmit information to,and/or receive information from, the eNB.

FIG. 2 shows an example wireless communication system 200. The wirelesscommunication system 200 depicts one base station 210 and one mobiledevice 250 for sake of brevity. However, it is to be appreciated thatsystem 200 can include more than one base station and/or more than onemobile device, wherein additional base stations and/or mobile devicescan be substantially similar or different from example base station 210and mobile device 250 described below. In addition, it is to beappreciated that base station 210 and/or mobile device 250 can employthe systems and methods described herein to facilitate wirelesscommunication there between. For example, components or functions of thesystems and/or methods described herein can be part of a memory 232and/or 272 or processors 230 and/or 270 described below, and/or can beexecuted by processors 230 and/or 270 to perform the disclosedfunctions.

At base station 210, traffic data for a number of data streams isprovided from a data source 212 to a transmit (TX) data processor 214.According to an example, each data stream can be transmitted over arespective antenna. TX data processor 214 formats, codes, andinterleaves the traffic data stream based on a particular coding schemeselected for that data stream to provide coded data.

The coded data for each data stream can be multiplexed with pilot datausing orthogonal frequency division multiplexing (OFDM) techniques.Additionally or alternatively, the pilot symbols can be frequencydivision multiplexed (FDM), time division multiplexed (TDM), or codedivision multiplexed (CDM). The pilot data is typically a known datapattern that is processed in a known manner and can be used at mobiledevice 250 to estimate channel response. The multiplexed pilot and codeddata for each data stream can be modulated (e.g., symbol mapped) basedon a particular modulation scheme (e.g., binary phase-shift keying(BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying(M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected forthat data stream to provide modulation symbols. The data rate, coding,and modulation for each data stream can be determined by instructionsperformed or provided by processor 230.

The modulation symbols for the data streams can be provided to a TX MIMOprocessor 220, which can further process the modulation symbols (e.g.,for OFDM). TX MIMO processor 220 then provides N_(T) modulation symbolstreams to N_(T) transmitters (TMTR) 222 a through 222 t. In variousembodiments, TX MIMO processor 220 applies beamforming weights to thesymbols of the data streams and to the antenna from which the symbol isbeing transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel.Further, N_(T) modulated signals from transmitters 222 a through 222 tare transmitted from N_(T) antennas 224 a through 224 t, respectively.

At mobile device 250, the transmitted modulated signals are received byN_(R) antennas 252 a through 252 r and the received signal from eachantenna 252 is provided to a respective receiver (RCVR) 254 a through254 r. Each receiver 254 conditions (e.g., filters, amplifies, anddownconverts) a respective signal, digitizes the conditioned signal toprovide samples, and further processes the samples to provide acorresponding “received” symbol stream.

An RX data processor 260 can receive and process the N_(R) receivedsymbol streams from N_(R) receivers 254 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. RX dataprocessor 260 can demodulate, deinterleave, and decode each detectedsymbol stream to recover the traffic data for the data stream. Theprocessing by RX data processor 260 is complementary to that performedby TX MIMO processor 220 and TX data processor 214 at base station 210.

The reverse link message can include various types of informationregarding the communication link and/or the received data stream. Thereverse link message can be processed by a TX data processor 238, whichalso receives traffic data for a number of data streams from a datasource 236, modulated by a modulator 280, conditioned by transmitters254 a through 254 r, and transmitted back to base station 210.

At base station 210, the modulated signals from mobile device 250 arereceived by antennas 224, conditioned by receivers 222, demodulated by ademodulator 240, and processed by a RX data processor 242 to extract thereverse link message transmitted by mobile device 250. Further,processor 230 can process the extracted message to determine whichprecoding matrix to use for determining beamforming weights.

Processors 230 and 270 can direct (e.g., control, coordinate, manage,etc.) operation at base station 210 and mobile device 250, respectively.Respective processors 230 and 270 can be associated with memory 232 and272 that store program codes and data. Moreover, processors 230 and 270can assist in performing counting procedures, described further herein.For example, processors 230 and 270 can execute functions described withrespect to such counting and/or memory 232 and 272 can store suchfunctions and/or data related thereto.

In an aspect, logical channels are classified into Control Channels andTraffic Channels. Logical Control Channels may include a BroadcastControl Channel (BCCH), which is a DL channel for broadcasting systemcontrol information; Paging Control Channel (PCCH), which is a DLchannel that transfers paging information; and Multicast Control Channel(MCCH), which may include a Point-to-multipoint DL channel used fortransmitting Multimedia Broadcast and Multicast Service (MBMS)scheduling and control information for one or several Multicast TrafficChannel (MTCHs). Generally, after establishing a Radio Resource Control(RRC) connection, this channel is used by UEs that receive MBMS.Dedicated Control Channel (DCCH) is a Point-to-point bi-directionalchannel that transmits dedicated control information and used by UEshaving an RRC connection. In one aspect, Logical Traffic Channelsincludes a Dedicated Traffic Channel (DTCH), which is a Point-to-pointbi-directional channel, dedicated to one UE, for the transfer of userinformation. Also, an MTCH for Point-to-multipoint DL channel fortransmitting traffic data may be used.

In an aspect, Transport Channels are classified into DL and UL. DLTransport Channels may include a Broadcast Channel (BCH), DownlinkShared Data Channel (DL-SDCH), and a Paging Channel (PCH). The PCH maybe used for support of UE power saving functions (e.g., discontinuousreception, or DRX, cycle is indicated by the network to the UE), and maybe broadcasted over an entire cell and mapped to PHY resources which canbe used for other control/traffic channels. The UL Transport Channelsmay include a Random Access Channel (RACH), a Request Channel (REQCH),an Uplink Shared Data Channel (UL-SDCH) and plurality of PHY channels.The PHY channels may include a set of DL channels and UL channels.

The DL PHY channels may include a: Common Pilot Channel (CPICH),Synchronization Channel (SCH), Common Control Channel (CCCH), Shared DLControl Channel (SDCCH), Multicast Control Channel (MCCH), Shared ULAssignment Channel (SUACH), Acknowledgement Channel (ACKCH), DL PhysicalShared Data Channel (DL-PSDCH), UL Power Control Channel (UPCCH), PagingIndicator Channel (PICH), and Load Indicator Channel (LICH).

The UL PHY Channels may include a: Physical Random Access Channel(PRACH), Channel Quality Indicator Channel (CQICH), AcknowledgementChannel (ACKCH), Antenna Subset Indicator Channel (ASICH), SharedRequest Channel (SREQCH), UL Physical Shared Data Channel (UL-PSDCH),and Broadband Pilot Channel (BPICH).

FIG. 3 illustrates a block diagram of a network 300 for use in an LTEsystem. In some aspects, the network 300 includes an evolved UMTSTerrestrial Radio Access Network (E-UTRAN). The E-UTRAN may be used toprovide wireless multimedia services, for example MBMSs, to one or moreUEs. The MBMSs may include mobile television, provision of films orother audiovisual works, and the distribution of other content such asdigital newspapers, for example. The E-UTRAN may be utilized toimplement a Multicast Broadcast Single Frequency Network (MBSFN). In anMBSFN, identical waveforms may be transmitted at substantially the sametime from multiple cells such that the waveforms are seen as a singletransmission by UEs receiving the waveforms. In some aspects, thenetwork 300 implements a mixed-carrier MBSFN.

The network 300 may include an eNB 302. As discussed above, the eNB 302may include an access point, for example the AP 100. The eNB maywirelessly communicate with one or more UEs, for example as illustratedin FIG. 1. In this way, the MBMSs may be wirelessly transmitted to theUEs in communication with the network 300. Although a single eNB 302 isillustrated in FIG. 3, a plurality of eNBs may be implemented in thenetwork 300.

The network 300 may further include a Multicell/Multicast CoordinationEntity (MCE) 304 in communication with the eNB 302 via an interface M2.The MCE 304 manages MBMS content and resources. In some aspects, the MCE304 determines a mode of delivering one or more MBMS. For example, theMCE 304 may optimize network resources such as by determining whetherthe eNB 302 provides an MBMS to a UE using point-to-point (p-t-p, alsoreferred to herein as unicast) transmission or point-to-multipoint(p-t-m, also referred to herein as multicast) transmission, or when totransition between the two (e.g., which can be based on a count ofdevices requesting one or more services). Further, the MCE 304 mayallocate time and frequency radio resources used by all eNBs in anMBSFN. Thus, a plurality of eNBs may be in communication with the MCE304, for example over respective M2 interfaces. The M2 interface mayinclude a control-plane interface, for example, that conveys sessioncontrol signaling to the eNB 302. This signaling may include radioconfiguration data for multicell MBSFN transmission.

The network 300 may further include a Mobility Management Entity (MME)306 in communication with the MCE 304 via an interface M3. The MME 306can be responsible for paging, including retransmission, and trackingUEs which are in an idle mode. The MME 306 may be used in the beareractivation/deactivation process and may also be responsible for choosinga serving gateway for UE at time of the UE initially attaching and atthe time of handover. The MME 306 may further be responsible forauthenticating users. The M3 interface may include a control-planeinterface, for example that carries session control signaling. Thissignaling may include session start and stop messages.

The network 300 may further include an MBMS Gateway (GW) 308 incommunication with the eNB 302 via an interface M1. The MBMS GW 308 maybroadcast packets to all eNBs within a service area. The MBMS GW 308 mayfurther be responsible for MBMS session management. The M1 interface mayinclude a user-plane interface. The M1 interface may use an IP multicastprotocol for delivery of packets to the eNB.

The network 300 may further include a Broadcast/Multicast Service Center(BM-SC) 312 in communication with the MBMS GW 308. The BM-SC 312 canserve as an entry point for content providers or otherbroadcast/multicast sources external to the network 300. In someaspects, the BM-SC 312 determines which UEs are allowed to register fora service, and stores a record of which UEs are currently registered forany given service, for example in a database of services. The BM-SC 312may also schedule broadcast and multicast sessions and provide MBMSsession announcements. In some aspects, the interfaces between theelements 302-312 of the network 300 (e.g., the M1-M3 interfaces, S_(m),and SG interfaces) may be referred to as the network backend orbackhaul.

FIG. 4 illustrates various components that may be utilized in a device400 that may be employed within the wireless communication systemdescribed with respect to FIG. 1 and/or the network 300 illustrated inFIG. 3. The device 400 is an example of a device that may be configuredto implement the various methods described herein. The wireless device400 may implement any of the devices illustrated in FIGS. 1-3.

The device 400 may include a processor 404 which controls operation ofthe device 400. The processor 404 may also be referred to as a centralprocessing unit (CPU). Memory 406, which may include both read-onlymemory (ROM) and random access memory (RAM), provides instructions anddata to the processor 404. A portion of the memory 406 may also includenon-volatile random access memory (NVRAM). The processor 404 may performlogical and arithmetic operations based on program instructions storedwithin the memory 406. The instructions in the memory 406 may beexecutable to implement the methods described herein. In some aspects,the processor 404 implements one or more of the TX data processor 214 or238, TX MIMO processor 220, processor 230 or 270, demodulator 240, RXdata processor 242 or 260, and modulator 280.

The processor 404 may include or be a component of a processing systemimplemented with one or more processors. The one or more processors maybe implemented with any combination of general-purpose microprocessors,microcontrollers, digital signal processors (DSPs), field programmablegate array (FPGAs), programmable logic devices (PLDs), controllers,state machines, gated logic, discrete hardware components, dedicatedhardware finite state machines, or any other suitable entities that canperform calculations or other manipulations of information.

The processing system may also include machine-readable media forstoring software. Software shall be construed broadly to mean any typeof instructions, whether referred to as software, firmware, middleware,microcode, hardware description language, or otherwise. Instructions mayinclude code (e.g., in source code format, binary code format,executable code format, or any other suitable format of code). Theinstructions, when executed by the one or more processors, cause theprocessing system to perform the various functions described herein.

The device 400 may also include a housing 408 that may include atransmitter 410 and a receiver 412 to allow transmission and receptionof data or instructions, for example wirelessly and/or over one of theinterfaces M1-M3 discussed above. The transmitter 410 and receiver 412may be combined into a transceiver 414. In some aspects, a single or aplurality of transmit antennas may be attached to the housing 408 andelectrically coupled to the transceiver 414. For example, when thedevice 400 is used to implement a UE or AT 116, or an AP 100 or eNB 302,the device 400 may include one or more antennas. The device 400 may alsoinclude (not shown) multiple transmitters, multiple receivers, and/ormultiple transceivers. In some aspects, the transmitter 410 includes oneor more of the transmitters 222 or 254 illustrated in FIG. 2. In someaspects, the receiver 412 includes one or more of the receivers 222 or254.

In some aspects, the device 400 also includes a signal detector 418 thatmay be used in an effort to detect and quantify the level of signalsreceived by the transceiver 414. The signal detector 418 may detect suchsignals and quantify the signals in terms of total energy, energy persubcarrier per symbol, power spectral density and other signals.

The device 400 may also include a digital signal processor (DSP) 420 foruse in processing signals. In some aspects, the DSP 420 implements oneor more of the TX data processor 214 or 238, TX MIMO processor 220,demodulator 240, RX data processor 242 or 260, and modulator 280.

The various components of the device 400 may be coupled together by abus system 422, which may include a power bus, a control signal bus, anda status signal bus in addition to a data bus. The device 400 mayfurther include other components or elements as will be understood bythose having ordinary skill in the art.

FIG. 5 illustrates communications 502 between an eNB, such as the eNB302 or the AP 100, and a UE, such as the AT 116 or 122. Thecommunications 502 are illustrated as being transmitted over the MCCH.As discussed above, the MCCH may include a Point-to-multipoint DLchannel used for transmitting MBMS scheduling and control information.Thus, the communications 502 may include information regarding wirelessservices for use by the UE. The communications may be used to indicatewhen a service is starting, for example, and the parameters of theservice. In some aspects, the communications 502 include a TemporaryMobile Group Identity (TMGI), which may uniquely identify an MBMS BearerService. The TMGI may be allocated by the BM-SC 312 and sent to the MCE304 for communication by the eNB 302 to UEs.

The communications 502 may be broadcast or multicast periodically fromthe eNB. The period between each broadcast is referred to as the MCCHrepetition period. When a network, such as the network 300, changes atleast some of the MCCH information, it may notify UEs about the changeduring a first modification period. In the next modification period, thenetwork may transmit the updated MCCH information. For example, thecommunications 502 a may notify any receiving UEs about a change in MCCHinformation, for example regarding the availability of certain MBMSs orthe delivery thereof. The information transmitted in the following MCCHperiod, however, can include different information. Thus, upon receivinga change notification in the communications 502 a, a UE interested toreceive MBMS services may acquire the new MCCH information from thecommunications 502 b, e.g., immediately from the start of themodification period n+1. The UE may apply the previously acquired MCCHinformation until the UE acquires new MCCH information.

In some aspects, indication of a radio network temporary identifier(RNTI), such as an MBMS RNTI (M-RNTI), on a Physical Downlink ControlChannel (PDCCH) is used to inform UEs in an idle mode, such as RRC_IDLEfor example, and UEs in a mode of being connected to the network, suchas RRC_CONNECTED for example, about an MCCH information change. Whenreceiving an MCCH information change notification, for example, in thecommunications 502 a during MCCH modification period n, the UE knowsthat the MCCH information changes at the next modification periodboundary, for example, the boundary with the MCCH modification periodn+1.

FIG. 6 depicts an example wireless communication system 600 for countingdevices to receive broadcast data in a wireless network. System 600includes a device 602 that communicates with a base station 604, asdescribed, to receive access to the wireless network. In addition,system 600 can include one or more core network components, such as aMCE 606, BM-SC 608, and/or other components not depicted (e.g., one ormore gateways, MMEs, or other connection managing nodes), with which thebase station 604 can communicate to provide the access. As described,base station 604 can broadcast signals related to one or more broadcastservices, and the MCE 606, BM-SC 608, etc., can provide one or morefunctions related to providing the services.

MCE 606 can include a registration information receiving component 610for obtaining information regarding a device registration for broadcastdata services, and a device counting component 612 for determining acount of devices registered to receive broadcast data services. MCE 606can also optionally include a counting request determining component 614for requesting counting from one or more base stations of devicesreceiving broadcast data services therefrom, and/or a broadcastdetermining component 616 for determining whether to provide a broadcastdata service.

BM-SC 608 can include a device registering component 618 for obtaining aregistration request from a device for broadcast data services, and aregistration information providing component 620 for communicatinginformation regarding the registration request to one or more corenetwork components.

According to an example, device 602 can register to receive broadcastdata from base station 604. For example, this can include communicatinga registration request to the base station 604 for the broadcast data(e.g., for an MBMS), which can forward the request to one or more corenetwork nodes, such as a BM-SC 608 for processing. In another example,device 602 can send a registration message to BM-SC 608 directly over auser plane that traverses multiple network nodes, such as a base station604, MCE 606, etc. This can be based on receiving a service announcementof broadcast data over one or more radio bearers. In one example, thedevice 602 can send the registration request over a unicast channel,and/or in a hypertext transfer protocol (HTTP) POST message, which caninclude a current time, location, etc., as described herein. Deviceregistering component 618 can obtain the request of the device 602, andcan determine whether to allow the device 602 to receive the broadcastdata (e.g., based on an authentication procedure, based on availableradio resources, etc.). In one example, BM-SC 608 can grant or deny theregistration request to the device 602. In addition, registrationinformation providing component 620 can communicate one or moreparameters related to the registration request to MCE 606. For example,this can be performed upon receiving the registration request, accordingto a timer or other event with one or more registration requests fromother devices, and/or the like.

Registration information receiving component 610 can obtain the one ormore parameters related to the registration request. In one example, theone or more parameters can include an indication of a registration froma device, an identity of the device 602, the location of the device, anindication of the broadcast service for which registration is requested,the registration request itself, and/or the like. Thus, for example,registration information receiving component 610 can obtain the one ormore parameters from the device 602 registration request, in one or moremessages from the BM-SC during or following the registration request,and/or the like.

Upon receiving the registration information, device counting component612 can increment a registration count of devices related to thebroadcast service for which registration is requested within the area.For example, device counting component 612 can store the registrationcount (e.g., in memory), and can increment the stored registrationcount. It is to be appreciated that other network devices can store theregistration count, and device counting component 612 can cause theother network devices to increment the registration count.

In any case, MCE 606 can utilize the registration count for variouspurposes, as described herein, such as a representative count of devicesfor a given broadcast data service, to determine whether to utilizeunicast or multicast transmission, to determine whether to enablebroadcast service counting requests (e.g., an eMBMS counting requestprocedure), and/or the like. In one example, based on the registrationcount, broadcast determining component 616 can determine whether toprovide a multicast broadcast data service. For example, where theregistration count is beyond a threshold, broadcast determiningcomponent 616 can instruct base station 604 and/or one or more otherbase stations to provide the multicast broadcast data service.

Moreover, for example, counting request determining component 614 candetermine whether to obtain a counting using counting requests based ona number of devices registered. For example, counting requestdetermining component 614 can compare a count of the number ofregistered devices to a threshold. For example, this can occur based ona timer or an event (e.g., such as device registration and/orderegistration). Where the number of registered devices is at least atthe threshold, for example, counting request determining component 614can determine to obtain counting using counting requests. In thisexample, counting request determining component 614 can communicatecounting requests to one or more base stations, such as base station604, and the base stations can accordingly broadcast counting requests,receive counting responses from one or more devices, and provide thenumber of counting responses received to MCE 606. For example, this cancorrelate to a Counting Request and Counting Response in eMBMS, asdescribed.

There can be more than one threshold, in other examples, such that wherethe registration count is beyond a first threshold but below a secondthreshold, counting request determining component 614 can determine toobtain counting using counting requests, and counting requestdetermining component 614 can accordingly communicate counting requeststo one or more base stations. Based on the counting responses, broadcastdetermining component 616 can determine whether to provide a multicastbroadcast data service. Where the registration count is beyond thesecond threshold, however, broadcast determining component 616 candetermine that the number of registered devices is sufficient enough toprovide a multicast broadcast data service without explicitly requestingcounting via counting requests.

In another example, device registering component 618 can similarlyreceive a request for deregistration of the broadcast data services fromthe device 602, and registration information providing component 620 cansimilarly inform MCE 606. Registration information receiving component610 can obtain the information regarding deregistration, and devicecounting component 612 can accordingly decrement the count of devicesreceiving the broadcast data service for which deregistration isrequested. In addition, broadcast determining component 616 candetermine whether to switch base station 604 to unicast transmissionbased in part on the count as decremented. In one example, countingrequest determining component 614 can determine whether to initiatecounting requests to verify the number of counting responses is belowthe threshold before switching to unicast transmission based on thenumber of device registrations decremented below a threshold. It is tobe appreciated that BM-SC 608 or another network component can similarlyinclude a device counting component 612 to maintain a count of devicesregistered to receive broadcast data services, and/or a counting requestdetermining component 614 for determining whether counting requestcounting is desired (e.g., and/or indicating such to the MCE 606).

FIG. 7 illustrates a system 700 for counting apparatuses receiving orinterested in a wireless service. System 700 includes a UE 702 thatcommunicates with an eNB 704 (e.g., over a Uu interface) for receivingaccess to a wireless network, as described. In addition, system 700includes core network components, such as an MCE 706, MME 708, MBMS-GW710, and/or BM-SC 712 for managing access to broadcast data services.For example, eNB 704 communicates with MCE 706 over an M2 interface, andMCE 706 communicates with MME 708 over an M3 interface in LTE. In thesystem 700, a quantity of apparatuses that are receiving or interestedin a service is determined based on UE registration for the service.Data that is kept at the BM-SC 712 regarding which UEs are registeredfor a given service may be sent to the MCE 706 for determination of themode of transmitting the service instead of, or as an indicator for, theMCE 706 requesting a count from the eNB 704.

For example, as shown, the UE 702 can read overhead messages todetermine MBSFN subframes and MCCH information 714 for determiningavailable eMBMSs. In addition, eNB 704 can provide aMBSFNAreaConfiguration 716 over the MCCH. The UE 702 receives a serviceannouncement 718 over an MBMS bearer or over a unicast bearer, which canoriginate from BM-SC 712 and be broadcast by eNB 704. The UE 702registers for the MBMS 720 with BM-SC 712, which can also include arequest for a MBMS service key (MSK). The procedure of registering maybe similar to the registration methods described herein. For example,the BM-SC 712 may be responsible for determining which MBMS servicesthat UEs may register and may store a record of the registered UEs, forexample in a database at the BM-SC 712. Registration may be requiredeven for data flows that do not require security protection. Theregistration from UEs may be backed off for randomized time to avoidnetwork congestions, and the registration message sent may includelocation information of the UE 702 that can be used by the network toestimate user density.

In this example, BM-SC 712 sends registration information 722 to the MCE706. In some aspects, the registration information for each UE is sentto MCE 706 as it is received or determined at the BM-SC 712. In otheraspects, the BM-SC 712 can wait for a period of time or collectinformation for a plurality of registration events before sending theregistration information to the MCE 706. The BM-SC 712 can also includethe registration information in an MBMS session start request messagewhich is sent from the BM-SC 712 to MCE 706 via MBMS-GW 710 and MME 708.In yet another aspect, the MCE 706 requests the registration informationfrom the BM-SC 712. The information sent to the MCE 706 may include notonly information regarding which UEs have registered for a service, butalso regarding any UEs that have deregistered from a service.Registration or deregistration can happen at any time.

The MCE 706 or BM-SC 712 may maintain a registration count of UEs thatare registered for one or more of the services, as described. Inresponse to the registration information, the registration count may beupdated such that the count reflects the current number of UEs that areregistered for a service within a service area or MBSFN area. In thisway, registration (subscription) information may be used to derive aneMBMS counting result. In another example, based on the registrationcount, MCE 706 can determine whether to count UEs using over the aircounting requests, as described. In another example, BM-SC 712 can makethe determination and indicate a counting mode to MCE 706. The BM-SC 712may send a session start request for the service 724. The MME 708 maysend a tracking area update (TAU) 726 to the MCE 706. The TAU mayinclude information regarding a location or location change of a UE 702.

In addition, the MCE 706 makes a decision as to a mode of transmittingthe service 728, and sends a session start request 730 to the eNB 704indicating the mode. The eNB 704 may communicate the start of thesession 732 to the registered UE 702 over the MCCH, for example using aMCCH change notification as described above with respect to FIG. 5. Whenthe service has ended, the session stop message may be sent over theMCCH. Further, a UE 702 may indicate that it does not wish to receivethe service any more by deregistering, as described. Moreover, eNB 704and MBMS-GW 710 can perform an Internet Group Management Protocol (IGMP)join 734, and BM-SC 712 can provide MBMS data 736 for broadcasting to UE702. MBMS-GW 710 can receive the MBMS data 738 and can provide the MBMSdata 738 to eNB 704 for broadcasting 740 to UE 702.

In this system 700, the network backend (e.g., MCE 706, MME 708, MBMS-GW710, and/or BM-SC 712) is used to collect a registration count. Thecount may be event driven, for example in response to each UEregistration or deregistration. In this example, not only can UEs inboth an idle mode and a connected mode be counted, legacy UEs thatregister for a service but do not have the functionality to respond toCounting Requests can also be counted since the counting isregistration-based. Moreover, such counting can conserve radio resourcesand/or UE power as compared to responding to periodic polling messages.

In some aspects, a UE 702 may provide the current time and/or locationwhen registering for an MBMS. In one example, the current location mayinclude the cell sector ID of the eNB 704 serving the UE 702. Thenetwork (e.g., the BM-SC 712 or other components) can use suchinformation to determine whether the UE 702 is allowed to register forthe MBMS, for example using the BM-SC 712 or based on informationregarding the transmission of services from the MCE 706. In someaspects, the network controls the percentage of UEs that are allowed toregister for a given broadcast data service. Therefore, when the UE 702indicates that it intends to consume or terminate consumption ofresources, by way of registering or deregistering, an eMBMS countingresult may be determined based on the registration count and the networkmay decide whether registration is allowed.

FIG. 8 illustrates a system 800 for counting apparatuses receiving orinterested in a wireless service. System 800 includes a UE 802 thatcommunicates with an eNB 804 for receiving access to a wireless network,as described. In addition, system 800 includes core network components,such as an MCE 806, MME 808, MBMS-GW 810, and/or BM-SC 812 for managingaccess to broadcast data services. The system 800 includescommunications similar to those shown in FIG. 7, and may be used whenthe current time/location is included in the registration request.

For example, as shown, the UE 802 can read overhead messages todetermine MBSFN subframes and MCCH information 814 for determiningavailable eMBMSs. In addition, eNB 804 can provide aMBSFNAreaConfiguration 816 over the MCCH. The UE 802 receives a serviceannouncement 818 over an MBMS bearer or over a unicast bearer. The UE802 sends a registration request 820 for the service, which is processedat least partially by the BM-SC 812. In some aspects, the registrationrequest may be sent using a HTTP POST procedure. The registrationrequest may include the current time and location of the UE. The BM-SC812 or another element in the network may determine whether to registerthe UE 802 for the service based at least in part on the time andlocation. The MCE 806 may also determine whether the UE 802 should beallowed to register, as discussed below.

The BM-SC may send a session start request 822 for the service. TheBM-SC 812 sends registration information 824 to the MCE 806. Asdiscussed above, the registration information may be used by the BM-SC812 or MCE 806 to maintain a registration count of UEs that areregistering for the service such that an eMBMS counting result may bedetermined. In some aspects, the BM-SC 812 sends the registrationinformation to the MCE 806 at 824 for determining the registrationcount.

The MCE 806 may receive a TAU 826 from the MME 808. The MCE 806 maydetermine whether the UE 802 should be allowed to register for theservice 828, for example based on the time and location information inthe registration request and/or the TAU received from the MME 808. TheMCE 806 alerts the BM-SC 812, which completes the registration or denialor registration, as described. The UE 802 is informed whether it hasbeen registered 830. In some aspects, the BM-SC 812 informs the UE 802using a Registration Response sent via a HTTP POST procedure.

The MCE 806 may determine a mode of transmitting the service, and sendsa session start request 832 to the eNB 804 indicating the mode. The eNB804 may communicate the start of the session 834 to the registered UE802 over the MCCH, for example, using a MCCH change notification asdescribed above with respect to FIG. 5. When the service has ended, thesession stop message may be sent over the MCCH. Further, a UE 802 mayindicate that it does not wish to receive the service any more byderegistering. Moreover, eNB 804 and MBMS-GW 810 can perform an IGMPjoin 836, and BM-SC 812 can provide MBMS data 838 for broadcasting to UE802. MBMS-GW 810 can receive the MBMS data 840 and can provide the MBMSdata 840 to eNB 804 for broadcasting 842 to UE 802.

The communications of system 800 include advantages similar to FIG. 7discussed above. Further, information about a UE 802 location at thetime of registration allows the MCE 806 to assess how many UEs in theMBSFN coverage area are currently accessing the service over the MBMSbearer, or are interested in accessing the service over the MBMS bearer.This information can be used by the MCE 806 independently of, orcomplementary to, count reporting from eNBs 804 to make MBSFNactivation/deactivation decisions.

FIG. 9 illustrates a system 900 of requesting counting of apparatusesreceiving or interested in a wireless service. System 900 includes a UE902 that communicates with an eNB 904 for receiving access to a wirelessnetwork, as described. In addition, system 900 includes core networkcomponents, such as an MCE 906, MME 908, MBMS-GW 910, and/or BM-SC 912for managing access to broadcast data services. In the system 900, theMCE 906 can request counting information from the BM-SC 912, which canoccur, for example, after registration information is received from theBM-SC 912 (e.g., as described in FIG. 8 at 824), or anytime after aneMBMS session has started.

For example, MCE 906 can transmit a MBMS service counting request 914 tothe BM-SC 912 to request counting information related to apparatusesreceiving or interested in a wireless service. In this example, theBM-SC 912 can respond with a MBMS service counting response 916, whichcan include a counting mode and registration information. The countingmode, for example, can specify whether to count a number of registereddevices, whether to broadcast Counting Requests, and/or the like, asdescribed. In addition, MME 908 can forward the MBMS service countingresponse at 918, which can include TAU information. For example, wherethe counting mode specifies that a count of registered devices can beused, MCE 906 can use a stored registration count, as described above,such that request/response counting can be avoided.

MCE 906 can make a decision 920 regarding whether to continue the MBMSsession or deactivate the session (e.g., based on a number of devicesregistered to receive the MBMS service, or a number of devices countedbased on the specified counting mode); for example, the session can havebeen started similarly as in FIG. 7 at 730, FIG. 8 at 832, etc. Forexample, the decision 920 can be based at least in part on the receivedcounting response(s). This can include at least one of whether responsesare received, a number of apparatuses indicated in the response(s),other registration information or TAU information in the responses,and/or the like, for example.

In the depicted example, the MCE 906 can optionally send a session stoprequest 922 based on the decision 920. For example, this can occur whereresponses to the counting request are not received and/or the responsesindicate a number of apparatuses receiving or interested in the wirelessservice as below a threshold level. In this example, the eNB 904 cantransmit a MBMS session stop 924 over MCCH to UEs that are in MBSFNarea, such as UE 902. It is to be appreciated, however, the MCE 906 candetermine 920 to continue the session based on received countingresponses. Also, in this example, eNB 904 and MBMS-GW 910 can perform aIGMP leave 926 based on discontinuation of the MBMS. Moreover, as aresult, eNB 904 can provide a related unicast service where one or moreUEs are still registered to receive the service, as described.

FIG. 10 shows an example wireless communication system 1000 forreporting counting of one or more devices receiving or at leastinterested in receiving broadcast data services. System 1000 includes adevice 1002 that communicates with a base station 1004 to receive accessto a core wireless network (not shown), as described. For example,system 1000 can allow the device 1002 to report counting based on arequest from base station 1004 where the device 1002 is communicating inidle mode. Idle mode communications, for example, can relate to device1002 powering off or reducing power to a transceiver except duringcertain time intervals during which base station 1004 can page device1002 to switch to an active mode to receive data from the base station1004. Thus, in idle mode, the device 1002 conserves radio resources, andcan resume active mode communications upon receiving a page and/or basedon an indication from an application or other process on the device 1002that network access is requested.

Device 1002 can include a counting request receiving component 1006 forobtaining a counting request from a base station, a communication modecomponent 1008 for operating device 1002 in one or more communicationmodes, and a counting request responding component 1010 for respondingto the counting request from the base station.

Base station 1004 can include a counting component 1012 for requestingand obtaining counting information from one or more devices, and a countreporting component 1014 for providing a count of devices receiving orinterested in receiving a broadcast data service to one or more corewireless network components.

According to an example, communication mode component 1008 can operatedevice 1002 in an idle mode, as described above. Count reportingcomponent 1014 can receive a request from the core wireless network toperform counting, as described herein, and counting component 1012 canaccordingly communicate a counting request to device 1002. For example,the counting request can correspond to a Counting Request in an eMBMSconfiguration or other counting request broadcasted to the device 1002.In one example, counting component 1012 can transmit the countingrequest in a paging message so the device 1002 can receive the countingrequest when operating in idle mode.

Counting request receiving component 1006 can obtain the countingrequest in the paging message, for example, and can determine whether torespond to the counting request. For example, counting request receivingcomponent 1006 can decode the paging message to obtain the countingrequest. In one example, the counting request can indicate one or moredevices that should respond to the counting request by indicating TMGIsor other identifiers that can be assigned to devices upon registering toreceive a certain broadcast data service, and counting requestresponding component 1010 can determine whether to respond to thecounting request based in part on whether device 1002 receives theindicated TMGI or other identifiers during registering to receive thebroadcast data service. In another example, the counting request sent bythe base station 1004 can indicate the broadcast data service to whichthe counting request relates, and counting request responding component1010 can determine whether to respond to the counting request based onwhether device 1002 has requested or otherwise indicated to receive therelated broadcast data service.

Where counting request responding component 1010 determines to respondto the counting request, this can occur immediately, within a period oftime, based on communication mode component 1008 switching to activemode for another purpose, and/or the like. Moreover, the response can bepart of an RRC Connection Request message or another messaging in anaccess procedure (e.g., a RACH procedure). For example, communicationmode component 1008 can switch to active mode upon counting requestresponding component 1010 determining to respond to the countingrequest, and counting request responding component 1010 can accordinglyrespond to the counting request while in active mode communications withbase station 1004. In another example, communication mode component 1008can switch to active mode for another purpose, such as to respond to apaging signal from base station 1004, receive the broadcast data servicefrom base station 1004, transmit data from an application on device1002, and/or the like. Upon transitioning to active mode, countingrequest responding component 1010 can respond to the counting request.

In one example, counting request responding component 1010 can respondto the counting request within an associated response time. For example,the response time can be received from the base station 1004 (e.g., inthe counting request, as a parameter during registration to receive thebroadcast data service, etc.), received in a configuration from thenetwork, received as a hardcoded parameter, and/or the like. In anexample, counting request responding component 1010 can wait for atleast a portion of the duration of the response time for communicationmode component 1008 to switch to active mode, and can accordinglytransmit the response in this case. If the communication mode component1008 does not switch to active mode within at least the portion of theduration, counting request responding component 1010 can causecommunication mode component 1008 to switch to active mode, and can thentransmit the response.

In another example, counting request receiving component 1006 can obtainthe request while communication mode component 1008 is operating device1002 in active mode communications. In this example, counting requestresponding component 1010 can transmit a response to the countingrequest, where so determined, while communication mode component 1008 isoperating device 1002 in the active mode. In another example, countingrequest receiving component 1006 can autonomously report counting to thebase station when the device 1002 communicates with the base station1004 in a connected mode for some other purposes, for example, receivingpaging signals, originating a unicast data call, and/or the like. Theautonomous reporting can also be based on updates of device's interestedMBMS services or receiving MBMS services have been changed. In any case,counting component 1012 can receive the response or autonomous reportfrom the device 1002 and/or other devices, and count reporting component1014 can provide the count to the core wireless network, for example.

FIG. 11 illustrates a system 1100 for counting apparatuses receiving orinterested in a wireless service. System 1100 includes a UE in idle mode1102 and/or a UE in connected mode 1104 that communicate with an eNB1106 for receiving access to a wireless network, as described. Inaddition, system 1100 includes core network components, such as an MCE1108, MME 1110, MBMS-GW 1112, and/or BM-SC 1114 for managing access tobroadcast data services. In the system 1100, UEs that are in an idlestate initiate a change to a connected state in part to respond to aCounting Request. The accuracy of the count may therefore be improvedbecause idle UEs can also be included in the count, as described aboveand further herein.

For example, as shown, the UEs 1102 and/or 1104 can read overheadmessages to determine MBSFN subframes and MCCH information 1116 fordetermining available eMBMSs. In addition, eNB 1106 can provide aMBSFNAreaConfiguration 1118 over the MCCH. The UEs 1102 and/or 1104receive a service announcement 1120 over an MBMS bearer or over aunicast bearer, which can originate from BM-SC 1114 and be broadcast byeNB 1106. The UEs 1102 and/or 1104 register for the MBMS 1122 and 1124with BM-SC 1114, which can also include a request for a MBMS service key(MSK). Moreover, BM-SC 1114 can send a session start request 1126 to MCE1108 to indicate beginning of the MBMS session. Further, MCE 1108 cantrigger counting procedures 1128 to eNB 1106, as described.

In one aspect of the system 1100, the UE 1102 receives a CountingRequest 1130 for one or more services, for example as described above.In one example, UE 1102 can receive the Counting Request in a pagingsignal from eNB 1106. If the UE 1102 determines that it is receiving theservice or interested in the service, and that it is in an idle, the UE1102 can initiate a change to a connected state. For example, a UE 1102in an RRC_IDLE mode may switch to a RRC_CONNECTED mode. To initiate thechange, the UE 1102 may send a random access preamble 1132 over a randomaccess channel to eNB 1106, such as the RACH. The preamble may be sentto contend for system resources, and may indicate that the UE 1102desires to transmit a message.

If the preamble is received by the eNB 1106 and resources have beenreceived for the message transmission, the eNB 1106 may transmit amessage 2 or other RACH response 1134 to the UE 1102 indicatingresources over which UE 1102 can request radio resources from eNB 1106.In some aspects, the response can be received over a downlink sharedchannel (DL-SCH).

The UE may respond with a connection request message 1136, for examplean RRCConnectionReq transmitted over a common control channel (CCCH).The request message may be used to request a unicast connection to theeNB 1106 such that the UE 1102 may send a response to the CountingRequest or for another purpose (e.g., in response to a paging message,in response to an application requesting network access, etc.). In anexample, the connection request message can include the response to thecounting message.

If the connection request is granted, a connection setup message 1138may be sent indicating the parameters of the unicast connection. Usingthese parameters—and where the connection request message does notinclude the response—the UE 1102 may transmit a Counting Responsemessage 1140 to the eNB 1106. In some aspects, as described, UEs thatwere previously idle respond a random period of time after obtaining theCounting Request 1130, respond when the UE switches to an active modefor another purposes, respond at least within a specified period oftime, etc. Some UEs may determine whether to respond after a randomamount of time based on coin-toss with a pre-advertised probabilitythreshold.

If the UE 1102 is going to return to the idle state after transmittingthe response, a connection release message 1142 may be transmitted tothe UE 1102 to release the unicast connection. For example, this canoccur where the UE 1102 switches to active mode for the purpose ofsending the response to the Counting Request (e.g., where a period oftime for sending the response is near expiration). In another example,UE 1104 can respond to the Counting Request 1130 with a CountingResponse message 1144, for example over the DCCH. Moreover, in any case,eNB 1106 can send a MBMS Service Counting Result Report 1146 includingthe Counting Result from at least UE 1102 and/or 1104 to MCE 1108.

In one example, MCE 1108 can determine that the counting resultsindicate to switch to multicast communications 1148. In this example,the MCE 1108 can send a session start request 1150 to eNB 1106. The eNB1106 may communicate the start of the session 1152 to the registered UE1104 over the MCCH, for example using a MCCH change notification asdescribed above with respect to FIG. 5. Moreover, eNB 1106 and MBMS-GW1112 can perform an IGMP join 1154, and BM-SC 1114 can provide MBMS data1156 for broadcasting to UE 1104. MBMS-GW 1112 can receive the MBMS data1158 and can provide the MBMS data 1158 to eNB 1106 for broadcasting1160 to UE 1104.

Using the system 1100, idle UEs may change to a connected state andrespond to the Counting Request. In this way, the counting result may bemore accurate. Switching to a connected state, however, may decreasebattery life and may increase the traffic in the network.

In another aspect of the system 1100, idle UEs may respond to theCounting Request received at 1130 without fully establishing a unicastconnection. This may reduce the overhead of initiating a change to aconnected stated, while still allowing idle UEs to respond.

In this aspect of the system 1100, a UE 1102 may include a response tothe Counting Request with the connection request message 1134. Forexample, the RRCConnectionReq includes an establishmentCause field inmany releases of LTE. The establishmentCause field may be set to acertain value to indicate that the UE 1102 is responding to the CountingRequest and to indicate the response. For example, the value can be anenumerated value defined to indicate that the UE 1102 is responding,such as countingResponse, which can be added to the establishmentCauseenumerations in LTE including emergency, highPriorityAccess, mt-Access,mo-Signalling, mo-Data, delayTolerantAccess-v1020, etc. In anotherexample, the indication can use one or more spare enumerations in theestablishmentCause element.

When the eNB 1106 receives the connection request message and identifiesthat the value has been set to indicate a response to the CountingRequest, the eNB 1106 may include the information indicated therein inthe Counting Result Report message. The eNB 1106 may also determine thata unicast connection need not be established, and the transmissions1138, 1140, and 1142 may be omitted. The eNB 1106 may therefore refrainfrom sending a further response to the UE 1102, in this example, and theUE 1102 may return to the idle state without receiving furthercommunication from the eNB 1106 and without completing the connectionprocedure. In any case, the accuracy of eMBMS is increased without asubstantial increase in resource utilization at the UE 1102 or thenetwork.

FIG. 12 illustrates a system 1200 for counting apparatuses receiving orinterested in a wireless service. System 1200 includes a UE 1202 thatcommunicates with an eNB 1204 for receiving access to a wirelessnetwork, as described. In addition, system 1200 includes core networkcomponents, such as an MCE 1206, MME 1208, MBMS-GW 1210, and/or BM-SC1212 for managing access to broadcast data services. Moreover, UE 1202,in this example, can notify a network when it activates a service toreceive broadcast data services.

For example, as shown, the UE 1202 can read overhead messages todetermine MBSFN subframes and MCCH information 1214 for determiningavailable eMBMSs. For example, such overhead messages can include systeminformation block (SIB) messages, such as SIB2, SIB13 and/or similarmessages. For example, from SIB2, UE 1202 can receive an indication ofMBSFN subframes, and from SIB13, UE 1202 obtains MCCH info, the locationof the PDCCH for MCCH change, etc. From PDCCH, UE 1202 can determineMCCH change notification. In addition, eNB 1204 can provide aMBSFNAreaConfiguration 1216 over the MCCH. The UE 1202 receives aservice announcement 1218 over an MBMS bearer or over a unicast bearer.The UE 1202 sends a registration request 1220 for the service, which isprocessed at least partially by the BM-SC 1212.

After registering for a service, the UE 1202 locally activates theservice to receive and process broadcast signals from eNB 1204. Inaddition, however, the UE 1202 transmits a message 1222, for example aMBMS service activation/deactivation message, to the eNB 1204 to notifythe eNB that the service has been activated. In some aspects, both idleUEs and connected UEs transmit this message to the eNB 1204.

In some aspects, a connection to the eNB 1204 can be used intransmitting the message notifying the eNB 1204 of the activation. Insuch aspects, idle UEs may initiate a change from an idle mode to aconnected mode as discussed above. An idle UE may fully establish aunicast connection, as discussed above, to notify the eNB 1204 of theservice activation, or the idle UE may use the abbreviated proceduredescribed above, including the notification in a field of the connectionrequest where the remaining messages typically used to establish theconnection are not sent.

The UE 1202 may also notify the eNB 1204 when it deactivates a service.Thus, the message 1222 may notify the eNB 1204 of a service deactivationinstead of service activation.

When the eNB 1204 receives the notification of service activation ordeactivation, the eNB 1204 may determine a Counting Result Reportmessage and send the Report 1224 to the MCE 1206. In some aspects, theReport includes information regarding from where an activation ordeactivation message is received. By monitoring activation/deactivationmessages of the UE 1202, and from where the messages are sent, thenetwork may determine the number of users in each cell related to agiven MBMS, as described.

The BM-SC 1212 can send a session start request 1226 to the MCE 1206based on the counting result, as described. MCE can trigger countingprocedures 1228 to eNB 1204, and can send session start request 1230.The eNB 1204 may communicate the start of the session 1232 to the UE1202 over the MCCH, for example, using a MCCH change notification asdescribed above with respect to FIG. 5. Moreover, eNB 1204 and MBMS-GW1210 can perform an IGMP join 1234, and BM-SC 1212 can provide MBMS data1236 for broadcasting to UE 1202. MBMS-GW 1210 can receive the MBMS data1238 and can provide the MBMS data 1238 to eNB 1204 for broadcasting1240 to UE 1202.

In some aspects, the eNB 1204 reports service activation/deactivationupon receiving notification form a UE. In other aspects, the eNB waitsfor a period of time and accumulates notifications from UEs beforesending the Counting Result Report message to the MCE. In still otheraspects, the UE 1202 sends the Report in response to a Counting Requestreceived from the MCE 1206. The MCE 1206 may use the Counting ResultReport message to determine a mode of service transmission, as describedabove.

FIG. 13 illustrates a system 1300 for counting apparatuses receiving orinterested in a wireless service. System 1300 includes a UE 1302 thatcommunicates with an eNB 1304 for receiving access to a wirelessnetwork, as described. In addition, system 1300 includes core networkcomponents, such as an MCE 1306, MME 1308, MBMS-GW 1310, and/or BM-SC1312 for managing access to broadcast data services. In the system 1300,the UE 1302 periodically transmits a Counting Response message to theeNB 1304. This periodic transmission may be performed even in theabsence of a Counting Request from the eNB 1304, for example.

For example, as shown, the UE 1302 can read overhead messages todetermine MBSFN subframes and MCCH information 1314 for determiningavailable eMBMSs. In addition, eNB 1304 can provide aMBSFNAreaConfiguration 1316 over the MCCH. The UE 1302 receives aservice announcement 1318 over an MBMS bearer or over a unicast bearer.The UE 1302 sends a registration request 1320 for the service, which isprocessed at least partially by the BM-SC 1312.

When registering for a service 1320, the UE 1302 may set a report periodtimer. When the report period timer expires 1332, the UE 1302 generatesand transmits a Counting Response message 1324. The report period timermay then be reset, and another Counting Response message sent upon thenext expiration of the timer. In this way, a Counting Response messagemay be transmitted by the UE 1302 at a period that is substantiallyequal to the report period.

In some aspects, the UE 1302 determines the report period based on areceived overhead message. For example, the report period may beincluded in an MBSFN configuration message as a timer value, a timeinterval, one or more explicit times, and/or the like. In some aspects,the UE 1302 determines the report period based on information receivedduring registration for the service 1320. For example, the BM-SC 1312may determine the report period during registration and notify the UE1302.

In some aspects, the UE 1302 determines which services to include in theCounting Response message based on an overhead message, and/or oninformation received during registration. In other aspects, the UE 1302is able to determine which services to report based on a type of theservices, or the UE 1302 is programmed to report certain of theservices.

The Counting Response message may be periodically generated and sent byUEs in a connected state, as well as UEs in an idle state. If a UE is inan idle state, the UE may initiate a change to the connected state asdescribed above with respect to the system 1300. When a UE is in theconnected mode, the UE may piggy back the Counting Response message on adata upload, and thereafter reset the timer. In this way, a separatetransmission would not be needed for the Counting Response message.

After receiving the Counting Result 1324, the eNB 1304 may send aCounting Result Report message 1326 to the MCE 1306. The Report may besent upon reception of the Counting Response message, or the MCE 1306may wait for a period of time or may wait for a request from the MCE1306, for example similar to the way in which the MCE 1306 operates toreport the service activation/deactivation in FIG. 12. The MCE 1306 mayuse the Counting Result Report message to determine a mode oftransmission for the reported services.

The BM-SC 1312 can send a session start request 1328 to the MCE 1306based on the counting result, as described. MCE can send session startrequest 1330 to eNB 1304. The eNB 1304 may communicate the start of thesession to the UE 1302 over the MCCH 1332, for example, using a MCCHchange notification as described above with respect to FIG. 5. Moreover,eNB 1304 and MBMS-GW 1310 can perform an IGMP join 1334, and BM-SC 1312can provide MBMS data 1336 for broadcasting to UE 1302. MBMS-GW 1310 canreceive the MBMS data 1338 and can provide the MBMS data 1338 to eNB1304 for broadcasting 1340 to UE 1202.

FIGS. 14-17 illustrate example methodologies relating to countingdevices requesting, interested in receiving, or otherwise related tobroadcast data. While, for purposes of simplicity of explanation, themethodologies are shown and described as a series of acts, it is to beunderstood and appreciated that the methodologies are not limited by theorder of acts, as some acts may, in accordance with one or moreembodiments, occur concurrently with other acts and/or in differentorders from that shown and described herein. For example, it is to beappreciated that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with one or more embodiments.

FIG. 14 illustrates a method 1400 for use with wireless services such asMBMS. In some aspects, a UE such as the AT 116, 122 may perform themethod 1400 to use an MBMS, for example based on information receivedover the MCCH as described above with respect to the communications 502illustrated in FIG. 5.

At 1402, an MBMS user service registration is performed by a UE. The UEmay accomplish this by transmitting a registration request to thenetwork. The BM-SC may determine whether the UE is allowed to registerfor the MBMS, and send a grant message to the eNB to transmit to the UEin response.

At 1404, a service announcement is received at the UE, for example overan MBMS bearer or a unicast bearer. At 1406, the UE locally activatesthe MBMS bearer service. The MBMS broadcast service activation proceduremay not register the user in the network, however, and may be a localprocedure. For example, an application executing on the UE can activatethe MBMS bearer service, which can include activating a receiver toattempt to decode signals received over a corresponding frequency of theMBMS. Thus, there generally is no MBMS bearer service specificsignalling exchanged between the UE and the network, and the broadcastservice activation procedure does not establish MBMS UE contexts in theUE, MME, and MBMS GW.

At 1408, the MBMS bearer service session starts, and the UE begins toreceive MBMS data from the eNB. The UE may receive services in either anidle mode or a connected mode. The connected mode may require signaltracking, synchronization, and feedback. In the connected mode, the UEmay transmit information back to the eNB using a unicast connection. Inthe idle mode, the UE may receive broadcasts of the MBMS withoutperforming all of the functions discussed above with respect to theconnected mode. In the idle mode, however, the UE cannot sendinformation back to the eNB.

At block 1410, an MBMS notification is received. Thereafter, at block1412, data is transferred, which can include the UE receiving data fromthe eNB. After the data is transferred, in one example, the session canbe stopped at block 1414, which can include receiving an indication ofthe stopped session from the eNB. For example, a BM-SC can command theeNB to stop the session based on one or more events (e.g., a response toa counting request received from the eNB specifying a number of UEsbelow a threshold). The MBMS bearer service may be subsequentlydeactivated at 1416. Similar to the activation, the deactivation istypically a local procedure. In this way, MBMS bearer services may beused by the UE.

FIG. 15 depicts an example methodology 1500 for counting registrationrequests to determine whether to request device counting in broadcastcommunications. At 1502, a registration request can be received forbroadcast data related to a device. For example, the request can be foran eMBMS, and can include a user service registration request over aunicast channel. In another example, the request can be received from aBM-SC relating to a request for the broadcast data.

At 1504, a registration count can be incremented based in part on theregistration request. The registration count can be stored in a memoryor other storage medium, and can be incremented for each registrationrequest received. In some examples, an identification of the device canbe verified with devices that have previously registered to preventmultiple registration counts for a single device. In another example,the registration count can be decremented for a deregistration requestreceived.

At 1506, it can be determined whether to request counting of devicesfrom one or more base stations based in part on the registration count.For example, if the number of registrations is at least at a threshold,counting can be requested to determine a count of devices receiving orinterested in receiving broadcast data. For example, the counting caninclude request/response counting (e.g., in eMBMS), as described. Inanother example, the registration count can be used for other purposesas well, such as to determine whether to use unicast or multicastcommunications for the broadcast data. Where the number of registrationsis below the threshold, for example, counting need not be requested, asdescribed herein. In another example, a broadcast mode can beactivated/deactivated based on the number of registrations with respectto the threshold.

FIG. 16 depicts an example methodology 1600 for determining whether toactivate MBSFN. At 1602, registration information and/or TAU informationcan be received from a BM-SC. For example, this can include receiving anindication of registration, parameters related to the registration,and/or the like. At 1604, it can be determined whether a thresholdnumber of UEs are registered in an area. The area, for example, can berelated to the TAU.

If the number of UEs registered in the area is at least at thethreshold, at 1606, MBSFN can be activated. This can include employingmultiple base stations to communicate broadcast data to the UEs. If thenumber of UEs registered in the area does not achieve the threshold, acounting request can be sent at 1608 to one or more base stations toobtain a more accurate count of devices actually receiving the broadcastdata. At 1610, it can be determined whether a threshold number (ofdevices) are indicated in responses. If so, at 1606, MBSFN can beactivated. If not, MBSFN can be deactivated or not enabled at 1614.

FIG. 17 shows an example methodology 1700 for responding to countingrequests received from a base station. At 1702, a counting request canbe received from a base station while communicating in an idle mode withthe base station. For example, the counting request can be received in apaging message from the base station, as described.

At 1704, communication with the base station can be switched to anactive mode. In one example, switching to the active mode can be basedon receiving the counting request or for another purpose (e.g., based ona paging signal received from the base station, a request for networkaccess from an application, etc.). In another example, the switch to theactive mode can be based on determining expiration of a period of timefrom receiving the counting request during which the active mode is notutilized for communicating with the base station.

In any case, once in the active mode, the counting request can beresponded to at 1706. For example, this can include communicating acounting response to the base station over a unicast channel establishedfor communication in the active mode.

It will be appreciated that, in accordance with one or more aspectsdescribed herein, inferences can be made regarding determining whetherto request counting and/or activate MBSFN based on a registration count,determining whether to switch to an active communication mode to respondto a counting request, and/or the like, as described. As used herein,the term to “infer” or “inference” refers generally to the process ofreasoning about or inferring states of the system, environment, and/oruser from a set of observations as captured via events and/or data.Inference can be employed to identify a specific context or action, orcan generate a probability distribution over states, for example. Theinference can be probabilistic—that is, the computation of a probabilitydistribution over states of interest based on a consideration of dataand events. Inference can also refer to techniques employed forcomposing higher-level events from a set of events and/or data. Suchinference results in the construction of new events or actions from aset of observed events and/or stored event data, whether or not theevents are correlated in close temporal proximity, and whether theevents and data come from one or several event and data sources.

FIG. 18 illustrates a system 1800 for determining whether to enabledevice counting based on a registration count. For example, system 1800can reside at least partially within a MCE, BM-SC, and/or the like. Itis to be appreciated that system 1800 is represented as includingfunctional blocks, which can be functional blocks that representfunctions implemented by a processor, software, or combination thereof(e.g., firmware). System 1800 includes a logical grouping 1802 ofelectrical components that can act in conjunction. For instance, logicalgrouping 1802 can include an electrical component for receiving aregistration request for broadcast data related to a device 1804. Thiscan be the registration request of the device, related informationreceived from a BM-SC, etc. Thus, the registration request can bereceived from the device in an uplink signal, from the BM-SC over a corenetwork communication, and/or the like. Logical grouping 1802 can alsoinclude an electrical component for incrementing a registration countbased in part on the registration request 1806. For example, theregistration count can be stored in a memory (e.g., memory 1810) and cancorrespond to a number of devices registered to receive a MBMS. Thus,electrical component 1806 can increment the stored registration countupon receiving registration requests from devices for the MBMS.

In addition, as described, electrical component 1806 can decrement theregistration count based on electrical component 1804 receiving aderegistration request. Logical grouping 1802 can also include anelectrical component for determining whether to request counting ofdevices from one or more base stations based in part on the registrationcount 1808. For example, this can be based on whether the storedregistration count is at least at a threshold. If so, counting can berequested from the one or more base stations, which can includecommunicating an indication to request counting to the one or more basestations over a network connection, as described. For example,electrical component 1804 can include a registration informationreceiving component 610, and electrical component 1806 can include adevice counting component 612, as described above. In addition, forexample, electrical component 1808, in an aspect, can include a countingrequest determining component 614, as described above.

Additionally, system 1800 can include a memory 1810 that retainsinstructions for executing functions associated with the electricalcomponents 1804, 1806, and 1808. While shown as being external to memory1810, it is to be understood that one or more of the electricalcomponents 1804, 1806, and 1808 can exist within memory 1810. Electricalcomponents 1804, 1806, and 1808, in an example, can be interconnectedover a bus 1812 or similar connection to allow communication among thecomponents. In one example, electrical components 1804, 1806, and 1808can include at least one processor, or each electrical component 1804,1806, and 1808 can be a corresponding module of at least one processor.Moreover, in an additional or alternative example, electrical components1804, 1806, and 1808 can be a computer program product including acomputer readable medium, where each electrical component 1804, 1806,and 1808 can be corresponding code.

FIG. 19 illustrates a system 1900 for responding to counting requestsfrom a base station. For example, system 1900 can reside at leastpartially within a device or other receiver. It is to be appreciatedthat system 1900 is represented as including functional blocks, whichcan be functional blocks that represent functions implemented by aprocessor, software, or combination thereof (e.g., firmware). System1900 includes a logical grouping 1902 of electrical components that canact in conjunction. For instance, logical grouping 1902 can include anelectrical component for receiving a counting request from a basestation while communicating in an idle mode with the base station 1904.For example, the counting request can be received in a paging messagefrom the base station. Logical grouping 1902 can also include anelectrical component for switching to an active mode for communicatingwith the base station 1906.

In an example, electrical component 1906 can switch to the active modeto communicate the counting request or for another purpose, asdescribed. Switching to active mode can include activating one or moreradio interfaces for communication with the one or more base stations.Logical grouping 1902 can also include an electrical component forresponding to the counting request while in the active mode 1908. Thecounting request can be responded to by transmitting a counting responseto the one or more base stations over an uplink connection thereto. Forexample, electrical component 1904 can include a counting requestreceiving component 1006, and electrical component 1906 can include acommunication mode component 1008, as described above. In addition, forexample, electrical component 1908, in an aspect, can include a countingrequest responding component 1010.

Additionally, system 1900 can include a memory 1910 that retainsinstructions for executing functions associated with the electricalcomponents 1904, 1906, and 1908. While shown as being external to memory1910, it is to be understood that one or more of the electricalcomponents 1904, 1906, and 1908 can exist within memory 1910. Electricalcomponents 1904, 1906, and 1908, in an example, can be interconnectedover a bus 1912 or similar connection to allow communication among thecomponents. In one example, electrical components 1904, 1906, and 1908can include at least one processor, or each electrical component 1904,1906, and 1908 can be a corresponding module of at least one processor.Moreover, in an additional or alternative example, electrical components1904, 1906, and 1908 can be a computer program product including acomputer readable medium, where each electrical component 1904, 1906,and 1908 can be corresponding code.

FIG. 20 is an illustration of a mobile device 2000 that facilitatesresponding to counting requests. Mobile device 2000 may include areceiver 2002 that receives a signal from, for instance, a receiveantenna (not shown), performs typical actions on (e.g., filters,amplifies, downconverts, etc.) the received signal, and digitizes theconditioned signal to obtain samples. Receiver 2002 can include ademodulator 2004 that can demodulate received symbols and provide themto a processor 2006 for channel estimation. Processor 2006 can be aprocessor dedicated to analyzing information received by receiver 2002and/or generating information for transmission by a transmitter 2008, aprocessor that controls one or more components of mobile device 2000,and/or a processor that both analyzes information received by receiver2002, generates information for transmission by transmitter 2008, andcontrols one or more components of mobile device 2000.

Mobile device 2000 can additionally include memory 2010 that isoperatively coupled to processor 2006 and that can store data to betransmitted, received data, information related to available channels,data associated with analyzed signal and/or interference strength,information related to an assigned channel, power, rate, or the like,and any other suitable information for estimating a channel andcommunicating via the channel. Memory 2010 can additionally storeprotocols and/or algorithms associated with estimating and/or utilizinga channel (e.g., performance based, capacity based, etc.).

It will be appreciated that the data store (e.g., memory 2010) describedherein can be either volatile memory or nonvolatile memory, or caninclude both volatile and nonvolatile memory. By way of illustration,and not limitation, nonvolatile memory can include read only memory(ROM), programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable PROM (EEPROM), or flash memory. Volatile memorycan include random access memory (RAM), which acts as external cachememory. By way of illustration and not limitation, RAM is available inmany forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).The memory 2010 of the subject systems and methods is intended toinclude, without being limited to, these and any other suitable types ofmemory.

Processor 2006 can further be optionally operatively coupled to acounting request receiving component 2012, which can be similar tocounting request receiving component 1006, a communication modecomponent 2014, which can be similar to communication mode component1008, and/or a counting request responding component 2016, which can besimilar to counting request responding component 1010.

Mobile device 2000 still further includes a modulator 2018 thatmodulates signals for transmission by transmitter 2008 to, for instance,a base station, another mobile device, etc. Moreover, for example,mobile device 2000 can include multiple transmitters 2008 for multiplenetwork interfaces, as described. Although depicted as being separatefrom the processor 2006, it is to be appreciated that the countingrequest receiving component 2012, communication mode component 2014,counting request responding component 2016, demodulator 2004, and/ormodulator 2018 can be part of the processor 2006 or multiple processors(not shown)), and/or stored as instructions in memory 2010 for executionby processor 2006.

FIG. 21 illustrates a computer device 2100 that can include an MCE 304,606, 706, 806, 906, 1108, 1206, 1306, etc., BW-SC 312, 612, 712, 812,912, 1114, 1212, 1312, etc. Computer device 2100 includes a processor2102 for carrying out processing functions associated with one or moreof components and functions described herein. Processor 2102 can includea single or multiple set of processors or multi-core processors.Moreover, processor 2102 can be implemented as an integrated processingsystem and/or a distributed processing system.

Computer device 2100 further includes a memory 2104, such as for storinglocal versions of applications being executed by processor 2102. Memory2104 can include substantially any type of memory usable by a computer,such as random access memory (RAM), read only memory (ROM), tapes,magnetic discs, optical discs, volatile memory, non-volatile memory, andany combination thereof. Computer device 2100 also includes one or morecomponents 2106-2122, which can be stored in memory 2104, executed byprocessor 2102 (e.g., based on instructions stored in memory 2104), beimplemented within one or more processors 2102, and/or the like.

Further, computer device 2100 includes a communications component 2106that provides for establishing and maintaining communications with oneor more parties utilizing hardware, software, and services as describedherein. Communications component 2106 may carry communications betweencomponents on computer device 2100, as well as between computer device2100 and external devices, such as devices located across acommunications network and/or devices serially or locally connected tocomputer device 2100. For example, communications component 2106 mayinclude one or more buses, and may further include transmit chaincomponents and receive chain components associated with a transmitterand receiver, respectively, operable for interfacing with externaldevices.

Additionally, computer device 2100 may further include a data store2108, which can be any suitable combination of hardware and/or software,that provides for mass storage of information, databases, and programsemployed in connection with aspects described herein. For example, datastore 2108 may be a data repository for applications not currently beingexecuted by processor 2102.

Computer device 2100 may optionally include an interface component 2110operable to receive inputs from a user of computer device 2100, andfurther operable to generate outputs for presentation to the user.Interface component 2110 may include one or more input devices,including but not limited to a keyboard, a number pad, a mouse, atouch-sensitive display, a navigation key, a function key, a microphone,a voice recognition component, any other mechanism capable of receivingan input from a user, or any combination thereof. Further, interfacecomponent 2110 may include one or more output devices, including but notlimited to a display, a speaker, a haptic feedback mechanism, a printer,any other mechanism capable of presenting an output to a user, or anycombination thereof. In another example, interface component 2110 can bean application programming interface (API) that can be accessed by oneor more devices to perform functions on computer device 2100.

In addition, in the depicted example, computer device 2100 canoptionally include one or more of a registration information receivingcomponent 2112, which can be similar to registration informationreceiving component 610, a device counting component 2114, which can besimilar to device counting component 612, a counting request determiningcomponent 2116, which can be similar to counting request determiningcomponent 614, a broadcast determining component 2118, which can besimilar to broadcast determining component 616, a device registeringcomponent 2120, which can be similar to device registering component618, and/or a registration information providing component 2122, whichcan be similar to registration information providing component 620.Thus, these components 2112, 2114, 2116, 2118, 2120, and/or 2122 canutilize processor 2102 to execute instructions associated therewith,memory 2104 to store information associated therewith, communicationscomponent 2106 to carry out communications, and/or the like, asdescribed. In addition, it is to be appreciated that computer device2100 can include additional or alternative components described herein.

FIG. 22 is an illustration of a system 2200 that facilitatescommunicating with one or more devices using wireless communications.System 2200 comprises a base station 2202, which can be substantiallyany base station (e.g., a small base station, such as a femtocell,picocell, etc., mobile base station . . . ), a relay, etc., having areceiver 2210 that receives signal(s) from one or more mobile devices2204 through a plurality of receive antennas 2206 (e.g., which can be ofmultiple network technologies, as described), and a transmitter 2228that transmits to the one or more mobile devices 2204 through aplurality of transmit antennas 2208 (e.g., which can be of multiplenetwork technologies, as described). In addition, in one example,transmitter 2228 can transmit to the mobile devices 2204 over a wiredfront link. Receiver 2210 can receive information from one or morereceive antennas 2206 and is operatively associated with a demodulator2212 that demodulates received information. In addition, in an example,receiver 2210 can receive from a wired backhaul link. Moreover, thoughshown as separate antennas, it is to be appreciated that at least onetransmit antenna 2208 can be combined with at least one receive antenna2206 as a single antenna. Demodulated symbols are analyzed by aprocessor 2214 that can be similar to the processor described above withregard to FIG. 20, and which is coupled to a memory 2216 that storesinformation related to estimating a signal (e.g., pilot) strength and/orinterference strength, data to be transmitted to or received from mobiledevice(s) 2204 (or a disparate base station (not shown)), and/or anyother suitable information related to performing the various actions andfunctions set forth herein.

Processor 2214 is further optionally coupled to counting component 2218,which can be similar to counting component 1012, and/or a countreporting component 2220, which can be similar to count reportingcomponent 1014. Moreover, for example, processor 2214 can modulatesignals to be transmitted using modulator 2226, and transmit modulatedsignals using transmitter 2228. Transmitter 2228 can transmit signals tomobile devices 2204 over Tx antennas 2208. Furthermore, althoughdepicted as being separate from the processor 2214, it is to beappreciated that the counting component 2218, count reporting component2220, demodulator 2212, and/or modulator 2226 can be part of theprocessor 2214 or multiple processors (not shown), and/or stored asinstructions in memory 2216 for execution by processor 2214.

The various illustrative logics, logical blocks, modules, components,and circuits described in connection with the embodiments disclosedherein may be implemented or performed with a general purpose processor,a digital signal processor (DSP), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may include one or more modules operable to perform one ormore of the steps and/or actions described above. An exemplary storagemedium may be coupled to the processor, such that the processor can readinformation from, and write information to, the storage medium. In thealternative, the storage medium may be integral to the processor.Further, in some aspects, the processor and the storage medium mayreside in an ASIC. Additionally, the ASIC may reside in a user terminal.In the alternative, the processor and the storage medium may reside asdiscrete components in a user terminal.

In one or more aspects, the functions, methods, or algorithms describedmay be implemented in hardware, software, firmware, or any combinationthereof. If implemented in software, the functions may be stored ortransmitted as one or more instructions or code on a computer-readablemedium, which may be incorporated into a computer program product.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable media that can be accessed by a computer. By way of example,and not limitation, such computer-readable media can include RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tocarry or store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, substantiallyany connection may be termed a computer-readable medium. For example, ifsoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs usually reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/orembodiments, it should be noted that various changes and modificationscould be made herein without departing from the scope of the describedaspects and/or embodiments as defined by the appended claims.Furthermore, although elements of the described aspects and/orembodiments may be described or claimed in the singular, the plural iscontemplated unless limitation to the singular is explicitly stated.Additionally, all or a portion of any aspect and/or embodiment may beutilized with all or a portion of any other aspect and/or embodiment,unless stated otherwise.

1. A method for counting devices related to broadcast data, comprising:receiving a registration request for broadcast data related to a device;incrementing a registration count based in part on the receiving theregistration request; and determining whether to request counting ofdevices from one or more base stations based in part on the registrationcount.
 2. The method of claim 1, further comprising determining whetherto utilize multicast communications for the broadcast data based in parton the registration count.
 3. The method of claim 1, further comprising:receiving a deregistration request from the device; and decrementing theregistration count based in part on the receiving the deregistrationrequest.
 4. The method of claim 1, further comprising transmittingcounting requests to the one or more base stations based on determiningto request counting of the devices.
 5. The method of claim 1, furthercomprising indicating to a multicast coordinating entity to requestcounting based in part on determining to request counting of thedevices.
 6. An apparatus for counting devices related to broadcast data,comprising: means for receiving a registration request for broadcastdata related to a device; means for incrementing a registration countbased in part on the registration request; and means for determiningwhether to request counting of devices from one or more base stationsbased in part on the registration count.
 7. The apparatus of claim 6,further comprising means for determining whether to utilize multicastcommunications for the broadcast data based in part on the registrationcount.
 8. The apparatus of claim 6, wherein the means for receivingreceives a deregistration request from the device, and the means forincrementing decrements the registration count based in part on thederegistration request.
 9. The apparatus of claim 6, wherein the meansfor determining transmits counting requests to the one or more basestations based on determining to request counting of the devices. 10.The apparatus of claim 6, wherein the means for determining indicates toa multicast coordinating entity to request counting based in part ondetermining to request counting of the devices.
 11. An apparatus forwireless communication, comprising: at least one processor configuredto: receive a registration request for broadcast data related to adevice; increment a registration count based in part on the registrationrequest; and determine whether to request counting of devices from oneor more base stations based in part on the registration count; and amemory coupled to the at least one processor.
 12. The apparatus of claim11, wherein the at least one processor is further configured todetermine whether to utilize multicast communications for the broadcastdata based in part on the registration count.
 13. The apparatus of claim11, wherein the at least one processor is further configured to: receivea deregistration request from the device; and decrement the registrationcount based in part on the receiving the deregistration request.
 14. Theapparatus of claim 11, wherein the at least one processor is furtherconfigured to transmit counting requests to the one or more basestations based on determining to request counting of the devices. 15.The apparatus of claim 11, wherein the at least one processor is furtherconfigured to indicate to a multicast coordinating entity to requestcounting based in part on determining to request counting of thedevices.
 16. A computer program product for counting devices related tobroadcast data, comprising: a non-transitory computer-readable medium,comprising: code for causing at least one computer to receive aregistration request for broadcast data related to a device; code forcausing the at least one computer to increment a registration countbased in part on the registration request; and code for causing the atleast one computer to determine whether to request counting of devicesfrom one or more base stations based in part on the registration count.17. An apparatus for counting devices related to broadcast data,comprising: a registration information receiving component for receivinga registration request for broadcast data related to a device; a devicecounting component for incrementing a registration count based in parton the registration request; and a counting request determiningcomponent for determining whether to request counting of devices fromone or more base stations based in part on the registration count. 18.The apparatus of claim 17, further comprising a broadcast determiningcomponent for determining whether to utilize multicast communicationsfor the broadcast data based in part on the registration count.
 19. Theapparatus of claim 17, wherein the registration information receivingcomponent receives a deregistration request from the device, and thedevice counting component decrements the registration count based inpart on the deregistration request.
 20. The apparatus of claim 17,wherein the counting request determining component transmits countingrequests to the one or more base stations based on determining torequest counting of the devices.
 21. The apparatus of claim 17, whereinthe counting request determining component indicates to a multicastcoordinating entity to request counting based in part on determining torequest counting of the devices.
 22. A method for broadcastcommunication with a base station, comprising: receiving a countingrequest related to receiving broadcast data from a base station whilecommunicating in an idle mode with the base station; switching to anactive mode for communicating with the base station; and responding tothe counting request while in the active mode.
 23. The method of claim22, wherein the switching to the active mode is based in part onreceiving the counting request.
 24. The method of claim 23, wherein theswitching to the active mode is based in part on determining that aperiod of time since receiving the counting request expires withoutswitching to the active mode.
 25. The method of claim 22, wherein theswitching to the active mode is based on a request from an applicationor receiving a paging signal from the base station.
 26. The method ofclaim 22, wherein the responding to the counting request comprisesincluding a response in one or more messages of a random accessprocedure.
 27. An apparatus for broadcast communication with a basestation, comprising: means for receiving a counting request related toreceiving broadcast data from a base station while communicating in anidle mode with the base station; means for switching to an active modefor communicating with the base station; and means for responding to thecounting request while in the active mode.
 28. The apparatus of claim27, wherein the means for switching switches to the active mode based inpart on the counting request.
 29. The apparatus of claim 28, wherein themeans for switching switches to the active mode based in part ondetermining that a period of time since receiving the counting requestexpires without switching to the active mode.
 30. The apparatus of claim27, wherein the means for switching switches to the active mode based ona request from an application or receiving a paging signal from the basestation.
 31. The apparatus of claim 27, wherein the means for respondingresponds to the counting request in part by including a response in oneor more messages of a random access procedure.
 32. An apparatus forwireless communication, comprising: at least one processor configuredto: receive a counting request related to receiving broadcast data froma base station while communicating in an idle mode with the basestation; switch to an active mode for communicating with the basestation; and respond to the counting request while in the active mode;and a memory coupled to the at least one processor.
 33. The apparatus ofclaim 32, wherein the at least one processor switches to the active modebased in part on the counting request.
 34. The apparatus of claim 33,wherein the at least one processor switches to the active mode based inpart on determining that a period of time since receiving the countingrequest expires without switching to the active mode.
 35. The apparatusof claim 33, wherein the at least one processor switches to the activemode based on a request from an application or receiving a paging signalfrom the base station.
 36. The apparatus of claim 33, wherein the atleast one processor responds to the counting request in part byincluding a response in one or more messages of a random accessprocedure.
 37. A computer program product for broadcast communicationwith a base station, comprising: a non-transitory computer-readablemedium, comprising: code for causing at least one computer to receive acounting request related to receiving broadcast data from a base stationwhile communicating in an idle mode with the base station; code forcausing the at least one computer to switch to an active mode forcommunicating with the base station; and code for causing the at leastone computer to respond to the counting request while in the activemode.
 38. An apparatus for broadcast communication with a base station,comprising: a counting request receiving component for receiving acounting request related to receiving broadcast data from a base stationwhile communicating in an idle mode with the base station; acommunication mode component for switching to an active mode forcommunicating with the base station; and a counting request respondingcomponent for responding to the counting request while in the activemode.
 39. The apparatus of claim 38, wherein the communication modecomponent switches to the active mode based in part on the countingrequest.
 40. The apparatus of claim 39, wherein the communication modecomponent switches to the active mode based in part on determining thata period of time since receiving the counting request expires withoutswitching to the active mode.
 41. The apparatus of claim 38, wherein thecommunication mode component switches to the active mode based on arequest from an application or a paging signal from the base station.42. The apparatus of claim 38, wherein the counting request respondingcomponent responds to the counting request in part by including aresponse in one or more messages of a random access procedure.